Transporting a Message from an Industrial End Device over an Ethernet Network

ABSTRACT

A method for transporting a message from an end device in an industrial plant over an Ethernet network with extended functionality for time-sensitive communication includes obtaining the message from a control application of the end device, mapping the message, based at least in part on the content of the message, to at least one functionality for time-sensitive communication converting the message into Ethernet frames; encoding a request to transport the message; transmitting the Ethernet frames; decoding the request; and forwarding the message on the Ethernet network according to the requested functionality for time-sensitive communication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to International PatentApplication No. PCT/EP2021/055794, filed on Mar. 8, 2021, which claimspriority to European Patent Application No. 20162481.4, filed on Mar.11, 2020, each of which is incorporated herein in its entirety byreference.

FIELD OF THE DISCLOSURE

The present disclosure relates to the communication of time-sensitivemessages from, to and between end devices in an industrial plant over anEthernet network.

BACKGROUND OF THE INVENTION

Industrial plants are increasingly fitted with Ethernet networks thatare enhanced with extended functionality for time-sensitivecommunication. Many “Industry 4.0” concepts assume that communicationover Ethernet with Time-Sensitive Network, TSN, functionality, incombination with Open Platform Communications Unified Architecture, OPCUA, will fully replace various control applications and fieldbuses. EP 2805 441 B1 discloses a method for configuring transmission of data overa packet switched data network between time-synchronized communicationmodules.

The useful service life of industrial end devices is typically muchlonger than the innovation cycle regarding the network communication.Some field devices may be in use for decades. An industrial plantnetwork built on OPC UA and TSN-enhanced Ethernet will therefore likelyhave to cope with end devices that are not TSN-aware for a foreseeablefuture.

BRIEF SUMMARY OF THE INVENTION

In one general aspect, the present disclosure provides systems andmethods that enhance the participation of end devices that are not awareof extended functionality for time-sensitive communication in anEthernet network that employs such functionality.

In one embodiment, the systems and methods in accordance with thedisclosure operate to transport a message from an end device in anindustrial plant over an Ethernet network with extended functionalityfor time-sensitive communication.

The disclosure describes a method for transporting a message from an enddevice in an industrial plant over an Ethernet network with extendedfunctionality for time-sensitive communication. In particular, thisfunctionality for time-sensitive communication may be Time-SensitiveNetworking, TSN, functionality. TSN functionality is in the process ofbeing standardized by the IEEE Time-Sensitive Networking Task Group.However, any other functionality for time-sensitive communication may beused as well in the context of the invention.

In the course of the method, an enabler component of the end deviceobtains the to-be-transported message from a control application of theend device. The enabler component may specifically comprise a softwarecomponent running on the same hardware platform as the controlapplication of the end device. Any suitable method provided by thehardware platform, and/or by an operating system on top of which thecontrol application and the enabler run, may then be used to convey themessage from the control application to the enabler component.Alternatively or in combination, the enabler component may comprise ahardware component. For example, such a hardware-component may be“piggy-backed” onto the end device and receive the message via afieldbus interface or other interface that the end device was originallydesigned to use in order to exchange messages.

The enabler component maps the message to at least one functionality fortime-sensitive communication that is to be used when transporting themessage over the Ethernet network. That is, the enabler component isaware of the functionality that is available in the Ethernet networkwhere the end device resides, and selects the functionality that is tobe used for the concrete message. In particular, such functionality maycomprise increasing the priority of particular messages over othertraffic in the Ethernet network, or even transmitting a particularmessage with a guarantee that it will reach its recipient within apredetermined time.

This selection (i.e., the mapping) is based at least in part on thecontent of the message, and/or on a path through which the message isdelivered to the enabler component. In particular, if the enablercomponent is to be used together with an existing control application,it is advantageous to analyze the content of the message and determinethe to-be-used functionality for time-sensitive communication based onthe result of this analysis. If there is the option of upgrading thecontrol application in the course of making the end device as a wholeaware of the functionality for time-sensitive communication, then thismay be facilitated by providing different paths on which the controlapplication may be transmitted to the enabler component. Specifically,by choosing a particular path, the control application may indicate apriority of the message to the enabler component. Figuratively speaking,the enabler component may provide differently colored in-trays formessages from the control application, and treat messages differentlyaccording to which in-tray they are put in.

The enabler component converts the message into one or more Ethernetframes. If the original message is already in the form of an Ethernetframe, this may comprise copying the original Ethernet frame andmodifying this as needed. If the original message is in a non-Ethernetformat, a new Ethernet frame may be created.

The enabler component encodes a request to transport the messageaccording to at least one functionality for time-sensitive communicationin at least one of said one more Ethernet frames and transmits the oneor more Ethernet frames onto the Ethernet network. At least one networkdevice of the Ethernet network decodes the request and forwards themessage on the Ethernet network according to the requested functionalityfor time-sensitive communication. In particular, the network device maybe a switch, a router, or a bridge.

Thus, the overall task of exploiting the new functionality fortime-sensitive communication when transporting messages from an enddevice that was previously not aware of this functionality is sharedbetween the enabler component and the network device. In particular, theencoding of the request by the enabler component and the converting ofthe decoded request into a concrete action introduce a layer ofabstraction that avoids, to a large extent, having to change the enablercomponent in response to changes to the Ethernet network and itsfunctionality for time-sensitive communication. In a particularindustrial plant, there are many more end devices than there are networkdevices, so leaving the enabler components on these end devicesuntouched when changes are made to the network saves a lot of work.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a flow chart of an exemplary embodiment for a method inaccordance with the disclosure.

FIG. 2 is a block diagram for an industrial plant having an end deviceand comprising an enabler component in accordance with the disclosure.

FIG. 3 is a schematic of an end device having multiple controlapplications and corresponding virtual interfaces in an enablercomponent in accordance with the disclosure.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic flow chart of an exemplary embodiment of themethod 100. In step 105, the enabler module 11 may be provisioned withconfiguration information 7 from a server 32 somewhere on the Ethernetnetwork 3 in the industrial plant 2 (not shown in FIG. 1 ).

In step 110, the enabler component 11 obtains the message 4 from acontrol application 12. Optionally, according to block 111, this maycomprise providing multiple virtual interfaces 13 a-13 c to the controlapplication 12.

In step 120, the message 4 is mapped to at least functionality 3* fortime-sensitive communication that is to be used when transporting themessage 4 over the Ethernet network 3. Inside box 120, two exemplarymanners are shown how this mapping may be performed.

According to block 121, the mapping may be performed according to thevirtual interface 13 a-13 c that has received the message 4.

According to block 122, it may be determined whether the message 4matches the condition 6 a of a rule 6 in a set of rules 6 in the enablermodule 11. If this is the case (truth value 1), according to block 123,the functionality 3* specified in the rule 6 may be chosen as thefunctionality 3* to use.

In step 130, the message 4 is converted into one or more Ethernet frames5. In step 140, the enabler component encodes a request 3** to transportthe message 4 according to functionality 3* for time-sensitivecommunication in one or more of the Ethernet frames 5. For this purpose,the Ethernet frames 5 may be modified and/or augmented.

The Ethernet frames 5 are transmitted onto the Ethernet network 3 instep 150. Optionally, according to block 151, a system time of theenabler component 11 may be synchronized with the Ethernet network 3, sothat the Ethernet frames 5 may be transmitted according to apredetermined schedule received from the network device 31.

The network device 31 is the first entity on the Ethernet network 3 thatprocesses the Ethernet frames 5. In step 160, the request 3** isdecoded, and so the network device 31 learns which functionality 3* fortime-sensitive communication shall be used when forwarding the message 4further onto the Ethernet network 3. This forwarding is performed instep 170.

FIG. 2 shows an exemplary end device 1 in an industrial plant 2 that iscovered by an Ethernet network 3. The Ethernet network 3 is drawn in bustopology only for simplicity; in reality, the Ethernet network 3 is aswitched network.

The end device 1 comprises a control application 12 that is not aware ofany functionality 3* for time-sensitive communication in the Ethernetnetwork 3. The control application 12 sends a message 4 that is meantfor a destination on the Ethernet network 3 to the enabler component 11.As discussed in connection with FIG. 1 , the enabler component 11produces a request 3 * * to user certain functionality 3* fortime-sensitive communication. This request 3** is decoded by the networkdevice 31, and the message 4, which had been passed to the networkdevice 31 in Ethernet frames 5, is passed on to its destinationsomewhere else on the Ethernet network 5, using the functionality 3*.

FIG. 3 shows an exemplary end device 1 in more detail. The end device 1comprises a hardware platform 10. On top of this platform 10, anoperating system kernel 15 runs. On top of the kernel 15, the controlapplication 12 and the enabler component 11 run. The enabler componentis further supplied with a notion of the current system time t byhardware clock 14 of the hardware platform 10.

In the example shown in FIG. 3 , the control application 12 has threedifferent modules 12 a-12 c. To each such module 12 a-12 c, the enablercomponent 11 provides a separate corresponding virtual interface 13 a-13c. The request 3** to use functionality 3* for time-sensitivecommunication relates to different functionality 3* depending on whichof the virtual interfaces 13 a-13 c received the message 4. That is, themessage 4 may be determined to be of higher or lower priority dependingon its source in the control application 12.

Furthermore, within enabler module 11, rules 6 for the treatment ofmessages 4 are defined. Each such rule defines at least one condition 6a and a corresponding functionality 3* for time-sensitive communication.If the condition 6 a is met, the functionality 3* shall be requested inthe request 3*.

For example, when carrying out the method in accordance with thedisclosure, at a first point in time, only one physical path may beavailable between a network device that serves a particular end deviceand a destination that is to receive a message from this end devicewithin a particular guaranteed time frame. To guarantee timely delivery,the network device has no choice but to defer the forwarding oflower-priority traffic. At a later point in time, a second physical lineis installed, and there is the new option of using this second physicalline for speedy delivery of the message. The enabler component stillonly needs to request the “what”, i.e., the timely delivery. The networkdevice takes care of the new “how”, i.e., which line to use and whatelse to do to guarantee timely delivery.

In an advantageous embodiment, the request is encoded in a priorityclass (such as a Quality of Service, QoS, field), and/or in a streamidentification parameter, of at least one Ethernet frame. For example,if the enabler component provides different paths (“in-trays”) formessages to the control application, then it may assign a differentstream identification parameter to the message depending on the paththat the control application chooses to convey the message. Whenmessages marked with different stream identification parameters arereceived by the network device, the network device may take appropriateaction when forwarding them.

Again, the sharing of the work between the enabler component and thenetwork device is advantageous if the concrete handling of the messagesis to be changed on a large scale. For example, if there is a qualityproblem in a final product, this may arouse the suspicion that achemical production process did not exactly follow its intended temporalrecipe because certain actions (such as opening or closing valves) tooktoo long to initiate over the Ethernet network. It may then becomenecessary to accelerate the transporting of all messages relating tosuch actions at the cost of the transporting of other messages. If theto-be-accelerated messages can be distinguished from the less importantmessages by their stream identifiers, then the change may be easilyimplemented by mapping these stream identifiers to different actions inthe network devices. The enabler components in the end devices (such ascontrollers and valves) may remain untouched.

For example, if the enabler component allows to produce traffic that ismapped to a particular QoS class using the VLAN tag and its priorityfield, the network device in a TSN-enabled network may recognize thistraffic and guarantee timely transport through the network, with limitsto upper boundaries of latency and jitter. In this context, “through thenetwork” means “between the first entry bridge port and the last exitbridge port”. Early evaluations suggest that such a scenario can ensuremillisecond latencies that suffice for most process automationrequirements. An end device equipped in this manner by means of theenabler component may be considered as “TSN-ready”.

In a particularly advantageous embodiment, the obtaining the messagefrom the control application of the end device specifically comprisesproviding, by the enabler component, to the control application, aplurality of virtual interfaces that are configured to receive themessage from the control application. The message may then be mapped tothe at least one functionality for time-sensitive communication based atleast in part on the virtual interface that has received the message.Thus, the virtual interfaces correspond to the “differently coloredin-trays” discussed before. If the control application is to be upgradedto avail itself of the new functionality for time-sensitivecommunication, this can be easily accomplished by having the controlapplication send the message to the enabler component via a differentvirtual interface. In particular, at least one virtual interface mayspecifically be a virtual Ethernet interface, a UNIX socket, a UNIXnamed pipe, a FIFO, a UNIX character device, or a UNIX block device. Forexample, in UNIX, a physical network interface that was previously usedto transmit all messages is easily augmented with a plurality of virtualnetwork interfaces that represent, e.g., different priorities ofmessages.

In a further particularly advantageous embodiment, the mapping of themessage to the at least one functionality for time-sensitivecommunication based on the content of the message is based on apredetermined set of rules in the enabler component. Each rule in thisset of rules contains at least a condition that relates to the contentof the message and associated the fulfilling of this condition with aconcrete functionality for time-sensitive communication that shall beused when transporting the message over the Ethernet network. Thus, forat least one rule, it is checked whether the condition required by thisrule is met, and if the condition is met, the functionality fortime-sensitive communication specified by this rule is selected as afunctionality to use.

These rules are rather specific to concrete end devices and the types ofmessages that can come from these end devices. It is thereforeadvantageous to administer them on the end devices, rather than on thenetwork devices of the Ethernet network.

For example, at least one condition required by at least one rule mayspecifically comprise that the end device indicates, by virtue of themessage, an abnormality it has detected. Specifically, the end devicemay indicate in this manner that it is in an abnormal state. Forexample, if a heating element does not complete an electric circuit witha power source despite being connected to the power source, this mayindicate that the heating element is broken and there is no conductivepath through it.

The end device may also indicate that a physical action performed by theend device on an industrial process executed by the industrial plant hasfailed. For example, after a valve has been instructed to open or closeand has actuated its drive mechanism to move the valve memberaccordingly, it may be checked with a proximity sensor whether the valvemember has actually reached the intended position or whether it isstuck.

Alternatively or in combination, at least one condition required by atleast one rule may comprise that a measurement value of a physicalquantity comprised in the message falls above or below a predeterminedthreshold value set in the at least one rule.

The rationale behind this is that many sensors are present in anindustrial plant for the purpose of detecting abnormal conditions. Aslong as there is no abnormality, there is no urgent need to follow, say,a temperature value that is bobbing up and down between 30° C. and 32°C. In a typical industrial plant, there will be a large flood of suchnon-urgent, normal measurement values. But when a sudden departure of ameasurement value from the normal state indicated a problem, immediateaction may be required. For example, if said temperature suddenly breaksout of the 30° C. to 32° C. band and shoots up to 40° C., this mayindicate that a cooling fan has stopped working, and a device has to beshut off immediately in order to avoid overheating.

In another example, the concrete current value that a valve motor drawswhile actuating the valve is not interesting most of the time. But ifthe current is lower than a certain threshold, then this may indicatethat the mechanical connection between the motor and the valve member isbroken, so that the motor does not act upon the valve member any more.If the current is higher than a certain threshold, this may indicatethat the movement of the valve member is impeded by an unusually highresistance, so that the valve member may be close to getting stuckaltogether.

In a further embodiment, the method further comprises synchronizing asystem time of the enabler component with the Ethernet network. If sucha synchronization has been achieved by the enabler component, then theone or more Ethernet frames may be transmitted from the enablercomponent to the Ethernet network, and thus to the network device, moreefficiently. For example, a notion of the exact time on the side of theenabler component allows the enabler component to transmit the one ormore Ethernet frames according to a schedule received by the enablercomponent from the at least one network device. If the end device isable to produce traffic that has a specific QoS mapping and istransmitted at a scheduled time, this may guarantee □s-granularprecision in data transport between any two end devices. The end devicemay then be deemed to have “full TSN support”.

There are three main types of industrial end devices for which it isparticularly advantageous to make them aware of the extendedfunctionality for time-sensitive communication.

As discussed above, an end device may specifically comprise a sensorthat is configured to measure at least one physical property. Thisphysical property is relevant for an industrial process executed by theindustrial plant, be it because it is a state variable of the processitself, or because it indicated the working state of equipment that isexecuting the industrial process.

As discussed above, the end device may comprise an actuator that isconfigured to perform a physical action on the industrial process.

The end device may also comprise a controller that is configured todrive one or more actuators and receive measurement values from at leastone sensor, so as to cause at least one quantity indicated by themeasurement values to move to, and/or to remain at, a predeterminedsetpoint value. For example, a controller may actuate inflow and outflowvalves of a reaction vessel, so as to keep a pressure or temperaturewithin the vessel at the setpoint value. Even in a normal operatingsituation, messages sent by the controller to one or more actuators maybe urgent. For example, the maximum slew rate with which the controllermay change the temperature or pressure in the vessel may depend on howfast the controller can open or close particular valves.

As discussed before, the final handling of the message with respect tothe extended functionality for time-sensitive communication isdetermined by a cooperation between the enabler component on the onehand, and a network device on the other hand. Some coordination betweenthose two entities is therefore needed. The enabler component may beconfigured up-front to cooperate with a particular network device whenit is installed. But it is very advantageous if changes to theconfiguration of the enabler component at run-time are possible. Forexample, a threshold value beyond which a measurement value will cause amessage to get a higher priority may need to be adjusted. Also, theimplementation of new functionality for time-sensitive communication inthe Ethernet network may prompt a corresponding augmentation of enablercomponents, so that the new functionality will actually be utilized to abetter extent.

Therefore, in a specially advantageous embodiment, the enabler componentreceives configuration from at least one server. This configurationinformation is indicative at least of one or more of:

-   -   how to map the message to the at least one functionality for        time-sensitive communication that is to be used when        transporting the message over the Ethernet network (this is        where, e.g., an adaptation of a threshold value is likely to        reside); and    -   how to encode, in the at least one of said one or more Ethernet        frames, the request to transport the message according to the at        least one functionality for time-sensitive communication (this        is where, e.g., utilization of new functionality is likely to        reside).

The transfer of configuration information from a server to the enablercomponent may be organized in any suitable manner.

For example, the enabler component may send a configuration pull requestto an enabler server in an Industry 4.0 engineering tool, and receivethe configuration in a pull reply. This is particularly useful when theneed to obtain a new configuration arises on the side of the enablercomponent, such as when the end device with the enabler component iscommissioned.

Alternatively or in combination, the enabler server may send theconfiguration to the enabler component in a push request, and theenabler component may confirm the updating of the configuration by meansof a configuration push reply. This is particularly useful when the needto update the configuration arises on the side of a centralizedmanagement, e.g., when deemed necessary by an operator.

Specifically, the enabler component may unify TSN invocation for allhigh-level protocols. This has the following advantages:

-   -   The TSN configuration flow is decoupled from the application        configuration flow.

Independently of the application, a seamless TSN configuration of theend device is enabled.

-   -   A unified TSN configuration entry point is provided for a system        builder. The system data flow configuration is enabled in an        application-independent manner.    -   TSN configuration items are abstracted from high-level        applications, so that applications will not need an application        programming interface, API, to invoke the TSN features on their        own.    -   The TSN API is abstracted from the embedded operating system. In        this manner, the high-level application will not need to        communicate with the (frequently proprietary) embedded system        interface.

The enabler server may come in the form of a plug-in module (e.g., alibrary) that may, e.g., be integrated into an existing engineeringtool. In particular, it may provide the following functionality:

-   -   Receive the TSN configuration items for end devices from, e.g.,        an engineering tool, a

CUC ora CNC;

-   -   cross-validate the configuration items with the plant-wide TSN        configuration (e.g., TSN bridges) via CUC/CNC if necessary;    -   send the configuration items to the end devices; and    -   trigger their deployment.

It should be noted that the enabler server is neither a networkscheduler is neither a pure configuration validator nor a networkscheduler. Rather, it is a plug-in module to deploy TSN configuration onend devices.

The enabler component may specifically receive the configuration itemsfrom the enabler server and use them to enable TSN on the end device,e.g., by:

-   -   invoking a legacy network interface from an operating system; or        wrapping the provided interface (in the case of a proprietary        format) to represent a legacy one;    -   configure an IEEE 802.1AS clock; and    -   configure a scheduler for a time-triggered communication.

The method may be wholly or partially computer-implemented. In thisrespect, hardware platforms of end devices, as well as network devices,are to be regarded as “computers” in a broad sense as well because thesedevices are able to execute at least the computer program code in theirfirmware. The invention therefore also provides one or more computerprograms with instructions that, when executed by one or more computers,cause the one or more computers to perform the method described above.

This computer program may be sold on a non-transitory computer storagemedium or as a download product that may be transmitted over a networkafter purchase. The invention therefore also relates to a non-transitorycomputer storage medium or a download product with the computer program.The invention also relates to one or more computers with the one or morecomputer programs, and/or with the non-transitory storage medium ordownload product.

LIST OF REFERENCE SIGNS

-   1 end device 1-   10 hardware platform of end device 1-   11 enabler component of end device 1-   12 control application of end device 1-   12 a-12 c modules of control application 12-   13 a-13 c virtual interfaces, provided by enabler component 11-   14 real-time clock of hardware platform 1-   15 operating system kernel of end device 1-   2 industrial plant-   3 Ethernet network in industrial plant 2-   3* functionality for time-sensitive communication in network 3-   3** request to use functionality 3*-   31 network device of Ethernet network 3-   32 configuration server in Ethernet network 3-   4 message-   5 Ethernet frames-   6 rule in enabler module 11-   6 a condition in rule 6-   7 configuration information for enabler module 11-   100 method-   105 obtaining configuration information 7 from server 32-   110 obtaining message from control application 12-   111 providing virtual interfaces 13 a-13 c to control application 12-   120 mapping message 4 to to-be-used functionality 3*-   121 performing mapping based on used virtual interface 13 a-13 c-   122 determining whether condition 6 a of rule 6 met-   123 determining functionality 3* according to matched rule 6-   130 converting message 4 into Ethernet frames 5-   140 encoding request 3** for functionality 3* into Ethernet frames 5-   150 transmitting Ethernet frames 5 to Ethernet network 3-   151 synchronizing system time of enabler module 11-   152 transmitting Ethernet frames 5 according to schedule-   160 decoding request 3** by network device 31-   170 forwarding message 4 by network device 31-   ttime

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

The use of the terms “a” and “an” and “the” and “at least one” andsimilar referents in the context of describing the invention (especiallyin the context of the following claims) are to be construed to coverboth the singular and the plural, unless otherwise indicated herein orclearly contradicted by context. The use of the term “at least one”followed by a list of one or more items (for example, “at least one of Aand B”) is to be construed to mean one item selected from the listeditems (A or B) or any combination of two or more of the listed items (Aand B), unless otherwise indicated herein or clearly contradicted bycontext. The terms “comprising,” “having,” “including,” and “containing”are to be construed as open-ended terms (i.e., meaning “including, butnot limited to,”) unless otherwise noted. Recitation of ranges of valuesherein are merely intended to serve as a shorthand method of referringindividually to each separate value falling within the range, unlessotherwise indicated herein, and each separate value is incorporated intothe specification as if it were individually recited herein. All methodsdescribed herein can be performed in any suitable order unless otherwiseindicated herein or otherwise clearly contradicted by context. The useof any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate the inventionand does not pose a limitation on the scope of the invention unlessotherwise claimed. No language in the specification should be construedas indicating any non-claimed element as essential to the practice ofthe invention.

Preferred embodiments of this invention are described herein, includingthe best mode known to the inventors for carrying out the invention.Variations of those preferred embodiments may become apparent to thoseof ordinary skill in the art upon reading the foregoing description. Theinventors expect skilled artisans to employ such variations asappropriate, and the inventors intend for the invention to be practicedotherwise than as specifically described herein. Accordingly, thisinvention includes all modifications and equivalents of the subjectmatter recited in the claims appended hereto as permitted by applicablelaw. Moreover, any combination of the above-described elements in allpossible variations thereof is encompassed by the invention unlessotherwise indicated herein or otherwise clearly contradicted by context.

What is claimed is:
 1. A method for transporting a message from an enddevice in an industrial plant over an Ethernet network with extendedfunctionality for time-sensitive communication, comprising the steps of:obtaining, by an enabler component of the end device, the message from acontrol application of the end device; mapping, by the enablercomponent, based at least in part on the content of the message, and/oron a path through which the message is delivered to the enablercomponent, the message to at least one functionality for time-sensitivecommunication that is to be used when transporting the message over theEthernet network; converting, by the enabler component, the message intoone or more Ethernet frames; encoding, by the enabler component, in atleast one of said one or more Ethernet frames, a request to transportthe message according to at least one functionality for time-sensitivecommunication; transmitting, by the enabler component, the one or moreEthernet frames onto the Ethernet network; decoding, by at least onenetwork device of the Ethernet network, the request; and forwarding, bythe at least one network device, the message on the Ethernet networkaccording to the requested functionality for time-sensitivecommunication.
 2. The method of claim 1, wherein the functionality fortime-sensitive communication specifically is Time-Sensitive Networking,TSN, functionality.
 3. The method of claim 1, wherein the request isencoded in a priority class, and/or in a stream identificationparameter, of at least one Ethernet frame.
 4. The method of claim 1,wherein the obtaining the message from the control application of theend device specifically comprises providing, by the enabler component,to the control application, a plurality of virtual interfaces that areconfigured to receive the message from the control application, andwherein the message is mapped to the at least one functionality fortime-sensitive communication based at least in part on the virtualinterface that has received the message.
 5. The method of claim 4,wherein at least one virtual interface is: a virtual Ethernet interface,a UNIX socket, a UNIX named pipe, a FIFO, a UNIX character device, or aUNIX block device.
 6. The method of claim 1, wherein the mapping of themessage to the at least one functionality for time-sensitivecommunication based on the content of the message specificallycomprises: determining, for at least one rule in a predetermined set ofrules in the enabler component, whether the content of the message meetsa condition required by this rule; and in response to determining thatthe condition is met, determining a functionality for time-sensitivecommunication specified by this rule as a functionality fortime-sensitive communication that is to be used when transporting themessage over the Ethernet network.
 7. The method of claim 6, wherein atleast one condition required by at least one rule specificallycomprises: the end device indicates, by virtue of the message, that itis in an abnormal state or that a physical action performed by the enddevice on an industrial process executed by the industrial plant hasfailed; and/or a measurement value of a physical quantity that iscomprised in the message falls above or below a predetermined thresholdvalue set in the at least one rule.
 8. The method of claim 1, furthercomprising: synchronizing a system time of the enabler component withthe Ethernet network.
 9. The method of claim 8, further comprising:transmitting the one or more Ethernet frames according to a schedulereceived by the enabler component from the at least one network device.10. The method of claim 1, wherein at least one end device specificallycomprises: a sensor that is configured to measure at least one physicalproperty that is relevant for an industrial process executed by theindustrial plant; an actuator that is configured to perform a physicalaction on said industrial process; and/or a controller that isconfigured to drive one or more actuators and receive measurement valuesfrom at least one sensor, so as to cause at least one quantity indicatedby the measurement values to move to, and/or to remain at, apredetermined setpoint value.
 11. The method of claim 1, furthercomprising: receiving, by the enabler component, configurationinformation from at least one server, wherein this configurationinformation is indicative at least of one or more of: how to map themessage to the at least one functionality for time-sensitivecommunication that is to be used when transporting the message over theEthernet network; and how to encode, in the at least one of said one ormore Ethernet frames, the request to transport the message according tothe at least one functionality for time-sensitive communication.
 12. Themethod of claim 1, wherein at least one enabler component specificallycomprises a software component running on the same hardware platform asthe control application of the end device.